Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1587

reference: 220-tree-1
name: 1587
tree-preservation-order: undefined
220-tpo-1
uprn
address-text
point: POINT (-1.041161 50.897523)
geometry: MULTIPOLYGON (((-1.041019 50.897508,-1.041026 50.897535,-1.041045 50.897561,-1.041076 50.897581,-1.041116 50.897594,-1.041160 50.897599,-1.041204 50.897595,-1.041244 50.897582,-1.041275 50.897562,-1.041296 50.897538,-1.041304 50.897510,-1.041297 50.897482,-1.041278 50.897457,-1.041247 50.897437,-1.041207 50.897424,-1.041163 50.897419,-1.041119 50.897423,-1.041079 50.897435,-1.041048 50.897455,-1.041027 50.897480,-1.041019 50.897508)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL